Data center traffic analytics synchronization

ABSTRACT

A network analytics system can receive first sensor data, including first network activity and a first timestamp associated with a first clock of a first node, and second sensor data, including second network activity and a second timestamp associated with a second clock of a second node. The system can determine a first delta between the first clock and a third clock based on the first timestamp, and a second delta between the second clock and the third clock. The system can determine a first communication latency associated with a first sensor of the first node, and a second communication latency associated with a second sensor of the second node. The system can generate a report that synchronizes one or more data flows between the first node and the second node based on the first delta, the second delta, the first communication latency, and the second communication latency.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No. 62/171,899, entitled “SYSTEM FOR MONITORING AND MANAGING DATACENTERS,” filed Jun. 5, 2015, and U.S. patent application Ser. No. 15/040,829, entitled “LATE DATA DETECTION IN DATA CENTER,” filed on Feb. 10, 2016, each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present technology pertains network analytics, and more specifically to synchronizing clocks of different systems in a computing environment.

BACKGROUND

Data centers typically include a large number of servers and virtual machines. Each server and virtual machine has its own internal clock, which it uses when generating any timestamps of network and system events. The accuracy of these timestamps is important when monitoring or managing the servers in these datacenters (e.g. identifying the sequence of events, correlating events, analytics of data flows and events, etc.). Monitoring a data center's servers can be especially problematic with third party monitors. Generally, these third party monitors are given limited access to these data centers (e.g. monitoring or observing the network activities of the datacenter). Additionally, the third party's internal clock of its system may not be synchronized to the data center's servers' clocks. As such, the third party will likely encounter a great deal of difficulties and problems when managing and monitoring the network of servers of the data center.

BRIEF DESCRIPTION OF THE FIGURES

In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only example embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates a diagram of an example network environment for implementing various embodiments of the present technology;

FIG. 2A illustrates a schematic diagram of an example sensor deployment in a virtualized environment;

FIG. 2B illustrates a schematic diagram of an example sensor deployment in an example network device;

FIG. 2C illustrates a schematic diagram of an example reporting system for implementing various embodiments of the present technology;

FIG. 2D illustrates a schematic diagram of an example sensor deployment for implementing various embodiments of the present technology;

FIG. 3A illustrates an example method for determining the clock differences between a sensor and a collector in accordance with various embodiments of the present technology;

FIG. 3B illustrates an example method for determining a communication latency associated with a communication channel between a sensor and a collector in accordance with various embodiments of the present technology;

FIGS. 4A and 4B illustrates an example system for determining a communication latency associated with a communication channel between a sensor and a collector in accordance with various embodiments of the present technology;

FIG. 5 illustrates an example network device; and

FIGS. 6A and 6B illustrate example system embodiments.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A network analytics system can receive first sensor data, including first network activity and a first timestamp associated with a first clock of a first node of a data center, and second sensor data, including second network activity and a second timestamp associated with a second clock of a second node of the data center. The network analytics system can determine a first delta between the first clock and a third clock of the network analytics system based on the first timestamp, and a second delta between the second clock and the third clock based on the second timestamp. The network analytics system can determine a first communication latency between the network analytics system and a first sensor of the first node, and a second communication latency between the network analytics system and a second sensor of the second node. The network analytics system can generate a report that synchronizes one or more data flows between the first node and the second node based on the first delta, the second delta, the first communication latency, and the second communication latency.

Description

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses a need for synchronizing clocks of various systems and entities in a given computing environment. For example, the disclosed technology can allow a host or node to synchronize its clock to the data center's clock. For instance, a synchronization of the timestamp(s)/clock(s) of the host(s) (or node(s) to the clock of a collector in the datacenter can be performed based on the clock of the collector. In other examples, the disclosed technology can also be implemented to address clock skew issues present in a computing environment. For instance, in some situations, even if the clocks of various entities within a computing environment are synchronized to some degree, greater precision may be desired when analyzing or monitoring the various entities or associated events and relationships (e.g., triggering events, process lineage, chronology, etc.).

FIG. 1 illustrates a diagram of an example network environment 100. Fabric 112 can represent the underlay (i.e., physical network) of network environment 100. Fabric 112 can include spine routers 1-N (102 _(A-N)) (collectively “102) and leaf routers 1-N (104 _(A-N)) (collectively “104”). Leaf routers 104 can reside at the edge of fabric 112, and can thus represent the physical network edge. Leaf routers 104 can be, for example, top-of-rack (“ToR”) switches, aggregation switches, gateways, ingress and/or egress switches, provider edge devices, and/or any other type of routing or switching device.

Leaf routers 104 can be responsible for routing and/or bridging tenant or endpoint packets and applying network policies. Spine routers 102 can perform switching and routing within fabric 112. Thus, network connectivity in fabric 112 can flow from the spine routers 102 to leaf routers 104, and vice versa.

Leaf routers 104 can provide servers 1-5 (106 _(A-E)) (collectively “106”), hypervisors 1-4 (108 _(A)-108 _(D)) (collectively “108”), and virtual machines (VMs) 1-5 (110 _(A)-110 _(E)) (collectively “110”) access to fabric 112. For example, leaf routers 104 can encapsulate and decapsulate packets to and from servers 106 in order to enable communications throughout environment 100. Leaf routers 104 can also connect other devices, such as device 114, with fabric 112. Device 114 can be any network-capable device(s) or network(s), such as a firewall, a database, a server, a collector 118 (further described below), an engine 120 (further described below), etc. Leaf routers 104 can also provide any other servers, resources, endpoints, external networks, VMs, services, tenants, or workloads with access to fabric 112.

VMs 110 can be virtual machines hosted by hypervisors 108 running on servers 106. VMs 110 can include workloads running on a guest operating system on a respective server. Hypervisors 108 can provide a layer of software, firmware, and/or hardware that creates and runs the VMs 110. Hypervisors 108 can allow VMs 110 to share hardware resources on servers 106, and the hardware resources on servers 106 to appear as multiple, separate hardware platforms. Moreover, hypervisors 108 and servers 106 can host one or more VMs 110. For example, server 106 _(A) and hypervisor 108 _(A) can host VMs 110 _(A-B).

In some cases, VMs 110 and/or hypervisors 108 can be migrated to other servers 106. For example, VM 110 _(A) can be migrated to server 106 _(C) and hypervisor 108 _(B). Servers 106 can similarly be migrated to other locations in network environment 100. For example, a server connected to a specific leaf router can be changed to connect to a different or additional leaf router. In some cases, some or all of the servers 106, hypervisors 108, and/or VMs 110 can represent tenant space. Tenant space can include workloads, services, applications, devices, and/or resources that are associated with one or more clients or subscribers. Accordingly, traffic in the network environment 100 can be routed based on specific tenant policies, spaces, agreements, configurations, etc. Moreover, addressing can vary between one or more tenants. In some configurations, tenant spaces can be divided into logical segments and/or networks and separated from logical segments and/or networks associated with other tenants.

Any of leaf routers 104, servers 106, hypervisors 108, and VMs 110 can include a sensor 116 configured to capture network data, and report any portion of the captured data to collector 118. Sensors 116 can be processes, agents, modules, drivers, or components deployed on a respective system (e.g., a server, VM, hypervisor, leaf router, etc.), configured to capture network data for the respective system (e.g., data received or transmitted by the respective system), and report some or all of the captured data to collector 118.

For example, a VM sensor can run as a process, kernel module, or kernel driver on the guest operating system installed in a VM and configured to capture data (e.g., network and/or system data) processed (e.g., sent, received, generated, etc.) by the VM. A hypervisor sensor can run as a process, kernel module, or kernel driver on the host operating system installed at the hypervisor layer and configured to capture data (e.g., network and/or system data) processed (e.g., sent, received, generated, etc.) by the hypervisor. A server sensor can run as a process, kernel module, or kernel driver on the host operating system of a server and configured to capture data (e.g., network and/or system data) processed (e.g., sent, received, generated, etc.) by the server. And a network device sensor can run as a process or component in a network device, such as leaf routers 104, and configured to capture data (e.g., network and/or system data) processed (e.g., sent, received, generated, etc.) by the network device.

Sensors 116 can be configured to report data and/or metadata about one or more packets, flows, communications, processes, events, and/or activities observed to collector 118. For example, sensors 116 can capture network data as well as information about the system or host of the sensors 116 (e.g., where the sensors 116 are deployed). Such information can also include, for example, data or metadata of active or previously active processes of the system, metadata of files on the system, system alerts, networking information, etc. Reported data from sensors 116 can provide details or statistics particular to one or more tenants. For example, reported data from a subset of sensors 116 deployed throughout devices or elements in a tenant space can provide information about the performance, use, quality, events, processes, security status, characteristics, statistics, patterns, conditions, configurations, topology, and/or any other information for the particular tenant space.

Additionally, the reports of sensors 116 can include timestamps associated with captured network traffic received, transmitted or generated by the host/node (e.g. VM, hypervisor, server, and leaf router). Sensors 116 can also associate a timestamp indicating when sensors 116 send the reports to collectors 118. Regardless, the timestamps can be based on the clock of the host (e.g., server, switch, VM, hypervisor, etc.) of where the sensor resides. For example, timestamps associated with sensors 116 residing on hypervisor 2 108 _(B) can be based on the clock of hypervisor 2 108 _(B). Furthermore, since multiple sensors 116 can reside on the same host, the reports of the multiple sensors 116 can be based on a same clock associated with the host or multiple clocks associated with the host. Collectors 118 can be one or more devices, modules, workloads and/or processes capable of receiving data from sensors 116. Collectors 118 can thus collect reports and data from sensors 116. Collectors 118 can be deployed anywhere in network environment 100 and/or even on remote networks capable of communicating with network environment 100. For example, one or more collectors can be deployed within fabric 112 or on one or more of the servers 106. One or more collectors can be deployed outside of fabric 112 but connected to one or more leaf routers 104. Collectors 118 can be part of servers 106 and/or separate servers or devices (e.g., device 114). Collectors 118 can also be implemented in a cluster of servers.

Collectors 118 can be configured to collect data from sensors 116. In addition, collectors 118 can be implemented in one or more servers. As previously noted, collectors 118 can include one or more collectors. Moreover, each collector can be configured to receive reported data from all sensors 116 or a subset of sensors 116. For example, a collector can be assigned to a subset of sensors 116 so the data received by that specific collector is limited to data from the subset of sensors.

Collectors 118 can be configured to aggregate data from all sensors 116 and/or a subset of sensors 116. Moreover, collectors 118 can be configured to analyze some or all of the data reported by sensors 116. For example, collectors 118 can include analytics engines (e.g., engines 120) for analyzing collected data. Environment 100 can also include separate analytics engines 120 configured to analyze the data reported to collectors 118. For example, engines 120 can be configured to receive collected data from collectors 118 and aggregate the data, analyze the data (individually and/or aggregated), generate reports, identify conditions, compute statistics, visualize reported data, troubleshoot conditions, visualize the network and/or portions of the network (e.g., a tenant space), generate alerts, identify patterns, calculate misconfigurations, identify errors, generate suggestions, generate testing, and/or any other analytics functions.

While collectors 118 and engines 120 are shown as separate entities, this is for illustration purposes as other configurations are also contemplated herein. For example, any of collectors 118 and engines 120 can be part of a same or separate entity. Moreover, any of the collector, aggregation, and analytics functions can be implemented by one entity (e.g., collectors 118) or separately implemented by multiple entities (e.g., engine 120 and/or collectors 118).

Each of the sensors 116 can use a respective address (e.g., internet protocol (IP) address, port number, etc.) of their host to send information to collectors 118 and/or any other destination. Moreover, sensors 116 can periodically send information about flows they observe to collectors 118. Sensors 116 can be configured to report each and every flow they observe. Sensors 116 can report a list of flows that were active during a period of time (e.g., between the current time and the time of the last report). The communication channel between a sensor and collector 118 can also create a flow in every reporting interval. Thus, the information transmitted or reported by sensors 116 can also include information about the flow created by the communication channel.

FIG. 2A illustrates a schematic diagram of an example sensor deployment 260 in a virtualized environment. Server 106 _(A) can run and host one or more VMs 202. VMs 202 can be configured to run workloads (e.g., applications, services, processes, functions, etc.) based on hardware resources 212 on server 106 _(A). VMs 202 can run on guest operating systems 206 on a virtual operating platform provided by hypervisor 208. Each VM can run a respective guest operating system which can be the same or different as other guest operating systems associated with other VMs on server 106 _(A). Moreover, each VM can have one or more network addresses, such as an internet protocol (IP) address. VMs 202 can thus communicate with hypervisor 208, server 106 _(A), and/or any remote devices or networks using the one or more network addresses.

Hypervisor 208 can be a layer of software, firmware, and/or hardware that creates and runs VMs 202. The guest operating systems running on VMs 202 can share virtualized hardware resources created by hypervisor 208. The virtualized hardware resources can provide the illusion of separate hardware components. Moreover, the virtualized hardware resources can perform as physical hardware components (e.g., memory, storage, processor, network interface, etc.), and can be driven by hardware resources 212 on server 106 _(A). Hypervisor 208 can have one or more network addresses, such as an internet protocol (IP) address, to communicate with other devices, components, or networks. For example, hypervisor 208 can have a dedicated IP address which it can use to communicate with VMs 202, server 106 _(A), and/or any remote devices or networks.

Hardware resources 212 of server 106 _(A) can provide the underlying physical hardware driving operations and functionalities provided by server 106 _(A), hypervisor 208, and VMs 202. Hardware resources 212 can include, for example, one or more memory resources, one or more storage resources, one or more communication interfaces, one or more processors, one or more circuit boards, one or more extension cards, one or more power supplies, one or more antennas, one or more peripheral components, etc. Additional examples of hardware resources are described below with reference to FIGS. 6 and 7.

Server 106 _(A) can also include one or more host operating systems. The number of host operating system can vary by configuration. For example, some configurations can include a dual boot configuration that allows server 106 _(A) to boot into one of multiple host operating systems. In other configurations, server 106 _(A) may run a single host operating system. Host operating systems can run on hardware resources 212. In some cases, hypervisor 208 can run on, or utilize, a host operating system on server 106 _(A).

Server 106 _(A) can also have one or more network addresses, such as an internet protocol (IP) address, to communicate with other devices, components, or networks. For example, server 106 _(A) can have an IP address assigned to a communications interface from hardware resources 212, which it can use to communicate with VMs 202, hypervisor 208, leaf router 104 _(A) in FIG. 1, collectors 118 in FIG. 1, and/or any remote devices or networks.

VM sensors 204 can be deployed on one or more of the VMs 202. VM sensors 204 can be data and packet inspection agents deployed on the VMs 202 to capture packets, flows, processes, events, traffic, and/or any data flowing through the VMs 202. VM sensors 204 can be configured to export or report any data collected or captured by the sensors 204 to a remote entity, such as collectors 118, for example. VM sensors 204 can communicate or report such data using a network address of the respective VMs 202 (e.g., VM IP address).

VM sensors 204 can capture and report any traffic (e.g., packets, flows, etc.) sent, received, generated, and/or processed by VMs 202. For example, sensors 204 can report every packet or flow of communication sent and received by VMs 202. Moreover, any communication sent or received by VMs 202, including data reported from sensors 204, can create a network flow. VM sensors 204 can report such flows to a remote device, such as collectors 118 illustrated in FIG. 1. VM sensors 204 can report each flow separately or aggregated with other flows. When reporting a flow, VM sensors 204 can include a sensor identifier that identifies sensors 204 as reporting the associated flow. VM sensors 204 can also include a flow identifier, an IP address, a timestamp, metadata, a process ID, and any other information, as further described below.

VM sensors 204 can also report multiple flows as a set of flows. When reporting a set of flows, VM sensors 204 can include a flow identifier for the set of flows and/or a flow identifier for each flow in the set of flows. VM sensors 204 can also include one or more timestamps and other information as previously explained.

VM sensors 204 can run as a process, kernel module, or kernel driver on the guest operating systems 206 of VMs 202. VM sensors 204 can thus monitor any traffic sent and received by VMs 202, any processes running on the guest operating systems 206, any workloads on VMs 202, etc.

Hypervisor sensor 210 can be deployed on hypervisor 208. Hypervisor sensor 210 can be a data inspection agent deployed on hypervisor 208 to capture traffic (e.g., packets, flows, etc.) and/or data flowing through hypervisor 208. Hypervisor sensor 210 can be configured to export or report any data collected or captured by hypervisor sensor 210 to a remote entity, such as collectors 118, for example. Hypervisor sensor 210 can communicate or report such data using a network address of hypervisor 208, such as an IP address of hypervisor 208.

Because hypervisor 208 can see traffic and data from VMs 202, hypervisor sensor 210 can also capture and report any data (e.g., traffic data) associated with VMs 202. For example, hypervisor sensor 210 can report every packet or flow of communication sent or received by VMs 202 and/or VM sensors 204. Moreover, any communication sent or received by hypervisor 208, including data reported from hypervisor sensor 210, can create a network flow. Hypervisor sensor 210 can report such flows to a remote device, such as collectors 118 illustrated in FIG. 1. Hypervisor sensor 210 can report each flow separately and/or in combination with other flows or data. When reporting a flow, hypervisor sensor 210 can include a sensor identifier that identifies hypervisor sensor 210 as reporting the flow. Hypervisor sensor 210 can also include a flow identifier, an IP address, a timestamp, metadata, a process ID, and any other information, as explained below.

Hypervisor sensor 210 can also report multiple flows as a set of flows. When reporting a set of flows, hypervisor sensor 210 can include a flow identifier for the set of flows and/or a flow identifier for each flow in the set of flows. Hypervisor sensor 210 can also include one or more timestamps and other information as previously explained.

As previously explained, any communication captured or reported by VM sensors 204 can flow through hypervisor 208. Thus, hypervisor sensor 210 can observe and capture any flows or packets reported by VM sensors 204. Accordingly, hypervisor sensor 210 can also report any packets or flows reported by VM sensors 204. For example, VM sensor A on VM A captures flow 1 (F1) and reports F1 to collector 118 on FIG. 1. Hypervisor sensor 210 on hypervisor 208 can also see and capture F1, as F1 would traverse hypervisor 208 when being sent or received by VM A. Accordingly, hypervisor sensor 210 on hypervisor 208 can also report F1 to collector 118. Thus, collector 118 can receive a report of F1 from VM sensor A on VM A and another report of F1 from hypervisor sensor 210 on hypervisor 208.

When reporting F1, hypervisor sensor 210 can report F1 as a message or a separate from the message or report of F1 transmitted by VM sensor A on VM A. However, hypervisor sensor 210 can also, or otherwise, report F1 as a message or report that includes or appends the message or report of F1 transmitted by VM sensor A on VM A. In other words, hypervisor sensor 210 can report F1 as a separate message or report from VM sensor A's message or report of F1, and/or a same message or report that includes both a report of F1 by hypervisor sensor 210 and the report of F1 by VM sensor A at VM A. In this way, VM sensors 204 at VMs 202 can report packets or flows received or sent by VMs 202, and hypervisor sensor 210 at hypervisor 208 can report packets or flows received or sent by hypervisor 208, including any flows or packets received or sent by VMs 202 and/or reported by VM sensors 204.

Hypervisor sensor 210 can run as a process, kernel module, or kernel driver on the host operating system associated with hypervisor 208. Hypervisor sensor 210 can thus monitor any traffic sent and received by hypervisor 208, any processes associated with hypervisor 208, etc.

Server 106 _(A) can also have a server sensor 214 running on it. Server sensor 214 can be a data inspection agent deployed on server 106 _(A) to capture data (e.g., packets, flows, traffic data, etc.) on server 106 _(A). Server sensor 214 can be configured to export or report any data collected or captured by server sensor 214 to a remote entity, such as collector 118, for example. Server sensor 214 can communicate or report such data using a network address of server 106 _(A), such as an IP address of server 106 _(A).

Server sensor 214 can capture and report any packet or flow of communication associated with server 106 _(A). For example, sensor 216 can report every packet or flow of communication sent or received by one or more communication interfaces of server 106 _(A). Moreover, any communication sent or received by server 106 _(A), including data reported from sensors 204 and 210, can create a network flow. Server sensor 214 can report such flows to a remote device, such as collector 118 illustrated in FIG. 1. Server sensor 214 can report each flow separately or in combination. When reporting a flow, server sensor 214 can include a sensor identifier that identifies server sensor 214 as reporting the associated flow. Server sensor 214 can also include a flow identifier, an IP address, a timestamp, metadata, a process ID, and any other information.

Server sensor 214 can also report multiple flows as a set of flows. When reporting a set of flows, server sensor 214 can include a flow identifier for the set of flows and/or a flow identifier for each flow in the set of flows. Server sensor 214 can also include one or more timestamps and other information as previously explained.

Any communications capture or reported by sensors 204 and 210 can flow through server 106 _(A). Thus, server sensor 214 can observe or capture any flows or packets reported by sensors 204 and 210. In other words, network data observed by sensors 204 and 210 inside VMs 202 and hypervisor 208 can be a subset of the data observed by server sensor 214 on server 106 _(A). Accordingly, server sensor 214 can report any packets or flows reported by sensors 204 and 210. For example, sensor A on VM A captures flow 1 (F1) and reports F1 to collector 118 on FIG. 1. Sensor 210 on hypervisor 208 can also see and capture F1, as F1 would traverse hypervisor 208 when being sent or received by VM A. In addition, sensor 214 on server 106 _(A) can also see and capture F1, as F1 would traverse server 106 _(A) when being sent or received by VM A and hypervisor 208. Accordingly, sensor 216 can also report F1 to collector 118. Thus, collector 118 can receive a report of F1 from sensor A on VM A, sensor 210 on hypervisor 208, and sensor 214 on server 106 _(A).

When reporting F1, server sensor 214 can report F1 as a message or report that is separate from any messages or reports of F1 transmitted by sensor A on VM A or sensor 210 on hypervisor 208. However, server sensor 214 can also, or otherwise, report F1 as a message or report that includes or appends the messages or reports or metadata of F1 transmitted by sensor A on VM A and sensor 210 on hypervisor 208. In other words, server sensor 214 can report F1 as a separate message or report from the messages or reports of F1 from sensor A and sensor 210, and/or a same message or report that includes a report of F1 by sensor A, sensor 210, and sensor 214. In this way, sensors 204 at VMs 202 can report packets or flows received or sent by VMs 202, sensor 210 at hypervisor 208 can report packets or flows received or sent by hypervisor 208, including any flows or packets received or sent by VMs 202 and reported by sensors 204, and sensor 214 at server 106 _(A) can report packets or flows received or sent by server 106 _(A), including any flows or packets received or sent by VMs 202 and reported by sensors 204, and any flows or packets received or sent by hypervisor 208 and reported by sensor 210.

Server sensor 214 can run as a process, kernel module, or kernel driver on the host operating system or a component of server 106 _(A). Server sensor 214 can thus monitor any traffic sent and received by server 106 _(A), any processes associated with server 106 _(A), etc.

In addition to network data, sensors 204, 210, and 214 can capture additional information about the system or environment in which they reside. For example, sensors 204, 210, and 214 can capture data or metadata of active or previously active processes of their respective system or environment, metadata of files on their respective system or environment, timestamps, network addressing information, flow identifiers, sensor identifiers, etc. Moreover, sensors 204, 210, 214 are not specific to any operating system environment, hypervisor environment, network environment, or hardware environment. Thus, sensors 204, 210, and 214 can operate in any environment.

As previously explained, sensors 204, 210, and 214 can send information about the network traffic they observe. This information can be sent to one or more remote devices, such as one or more servers, collectors, engines, etc. Each sensor can be configured to send respective information using a network address, such as an IP address, and any other communication details, such as port number, to one or more destination addresses or locations. Sensors 204, 210, and 214 can send metadata about one or more flows, packets, communications, processes, events, etc.

Sensors 204, 210, and 214 can periodically report information about each flow or packet they observe. The information reported can contain a list of flows or packets that were active during a period of time (e.g., between the current time and the time at which the last information was reported). The communication channel between the sensor and the destination can create a flow in every interval. For example, the communication channel between sensor 210 and collector 118 can create a control flow. Thus, the information reported by a sensor can also contain information about this control flow. For example, the information reported by sensor 210 to collector 118 can include a list of flows or packets that were active at hypervisor 208 during a period of time, as well as information about the communication channel between sensor 210 and collector 118 used to report the information by sensor 210.

The report(s) of sensors 204, 210, and 214 can include timestamps associated with captured network traffic received, transmitted or generated by the host/node (e.g. VM 3 202, hypervisor 208 and server 106 _(A)). Sensors 204, 210, and 214 can also associate a timestamp indicating when each respective sensor 204, 210, and 214 transmits its respective report(s) to the remote device, such as collectors 118 illustrated in FIG. 1. Regardless, the timestamps associated by sensors 204, 210, and 214 can be based on the clock of the host/node (e.g. VM 3 202, hypervisor 208 and server 106 _(A)) where each respective sensor resides.

FIG. 2B illustrates a schematic diagram of an example sensor deployment 220 in an example network device. Network device is described as leaf router 104 _(A). However, this is for explanation purposes. Network device can be any other network device, such as any other switch, router, etc.

In this example, leaf router 104 _(A) can include network resources 222, such as memory, storage, communication, processing, input, output, and other types of resources. Leaf router 104 _(A) can also include an operating system environment 224. The operating system environment 224 can include any operating system, such as a network operating system. The operating system environment 224 can include processes, functions, and applications for performing networking, routing, switching, forwarding, policy implementation, messaging, monitoring, and other types of operations.

Leaf router 104 _(A) can also include sensor 226. Sensor 226 can be an agent configured to capture network data, such as flows or packets, sent and received by leaf router 104 _(A). Sensor 226 can also be configured to capture other information, such as processes, statistics, alerts, status information, device information, etc. Moreover, sensor 226 can be configured to report captured data to a remote device or network, such as collector 118, for example. Sensor 226 can report information using one or more network addresses associated with leaf router 104 _(A). For example, sensor 226 can be configured to report information using an IP assigned to an active communications interface on leaf router 104 _(A).

Leaf router 104 _(A) can be configured to route traffic to and from other devices or networks, such as server 106 _(A). Accordingly, sensor 226 can also report data reported by other sensors on other devices. For example, leaf router 104 _(A) can be configured to route traffic sent and received by server 106 _(A) to other devices. Thus, data reported from sensors deployed on server 106 _(A), such as VM and hypervisor sensors on server 106 _(A), would also be observed by sensor 226 and can thus be reported by sensor 226 as data observed at leaf router 104 _(A). Data reported by the VM and hypervisor sensors on server 106 _(A) can therefore be a subset of the data reported by sensor 226.

The report(s) of sensors 226 can include timestamps associated with captured network traffic received, transmitted or generated by the host/node (e.g. operating system environment 224 and network resources 222). Sensors 226 can also associate a timestamp indicating when each respective sensor 226 transmits its respective report(s) to the remote device, such as collectors 118 illustrated in FIG. 1. Regardless, the timestamps associated by sensors 226 can be based on a clock of the host/node (e.g. operating system environment 224 and network resources 222) where each respective sensor resides.

Sensor 226 can run as a process or component (e.g., firmware, module, hardware device, etc.) in leaf router 104 _(A). Moreover, sensor 226 can be installed on leaf router 104 _(A) as a software or firmware agent. In some configurations, leaf router 104 _(A) itself can act as sensor 226. Moreover, sensor 226 can run within the operating system 224 and/or separate from the operating system 224.

FIG. 2C illustrates a schematic diagram of an example reporting system 240 in an example sensor topology. Leaf router 104 _(A) can route packets or traffic 242 between fabric 112 and server 106 _(A), hypervisor 108 _(A), and VM 110 _(A). Packets or traffic 242 between VM 110 _(A) and leaf router 104 _(A) can flow through hypervisor 108 _(A) and server 106 _(A). Packets or traffic 242 between hypervisor 108 _(A) and leaf router 104 _(A) can flow through server 106 _(A). Finally, packets or traffic 242 between server 106 _(A) and leaf router 104 _(A) can flow directly to leaf router 104 _(A). However, in some cases, packets or traffic 242 between server 106 _(A) and leaf router 104 _(A) can flow through one or more intervening devices or networks, such as a switch or a firewall.

Moreover, VM sensor 116 at VM 110 _(A), hypervisor sensor 116 at hypervisor 108 _(A), network device sensor 116 at leaf router 104 _(A), and any server sensor at server 106 _(A) (e.g., sensor running on host environment of server 106 _(A)), can send reports 244 to collector 118 based on the packets or traffic 242 captured at each respective sensor. Reports 244 from VM sensor 116 to collector 118 can flow through VM 110 _(A), hypervisor 108 _(A), server 106 _(A), and leaf router 104 _(A). Reports 244 from hypervisor sensor 116 to collector 118 can flow through hypervisor 108 _(A), server 106 _(A), and leaf router 104 _(A). Reports 244 from any other server sensor at server 106 _(A) to collector 118 can flow through server 106 _(A) and leaf router 104 _(A). Finally, reports 244 from network device sensor 116 to collector 118 can flow through leaf router 104 _(A).

Reports 244 can include any portion of packets or traffic 242 captured at the respective sensors. Reports 244 can also include other information, such as timestamps, process information, sensor identifiers, flow identifiers, flow statistics, notifications, logs, user information, system information, etc. Moreover, reports 244 can be transmitted to collector 118 periodically as new packets or traffic 242 are captured by a sensor. Further, each sensor can send a single report or multiple reports to collector 118. For example, each of the sensors 116 can be configured to send a report to collector 118 for every flow, packet, message, communication, or network data received, transmitted, and/or generated by its respective host (e.g., VM 110 _(A), hypervisor 108 _(A), server 106 _(A), and leaf router 104 _(A)). As such, collector 118 can receive a report of a same packet from multiple sensors.

The reports 224 of sensors 116 can include timestamps associated with captured network traffic received, transmitted or generated by the host/node (VM 110 _(A), hypervisor 108 _(A), server 106 _(A), and leaf router 104 _(A)). Sensors 116 can also associate a timestamp indicating when each of the sensors 116 transmits reports 224 to the collector 118. Regardless, the timestamps associated by sensors 226 can be based on a clock of the host/node (e.g. VM 110 _(A), hypervisor 108 _(A), server 106 _(A), and leaf router 104 _(A)) where each of the respective sensors 116 resides.

For example, a packet received by VM 110 _(A) from fabric 112 can be captured and reported by VM sensor 116. Since the packet received by VM 110 _(A) will also flow through leaf router 104 _(A) and hypervisor 108 _(A), it can also be captured and reported by hypervisor sensor 116 and network device sensor 116. Thus, for a packet received by VM 110 _(A) from fabric 112, collector 118 can receive a report of the packet from VM sensor 116, hypervisor sensor 116, and network device sensor 116.

Similarly, a packet sent by VM 110 _(A) to fabric 112 can be captured and reported by VM sensor 116. Since the packet sent by VM 110 _(A) will also flow through leaf router 104 _(A) and hypervisor 108 _(A), it can also be captured and reported by hypervisor sensor 116 and network device sensor 116. Thus, for a packet sent by VM 110 _(A) to fabric 112, collector 118 can receive a report of the packet from VM sensor 116, hypervisor sensor 116, and network device sensor 116.

On the other hand, a packet originating at, or destined to, hypervisor 108 _(A), will can be captured and reported by hypervisor sensor 116 and network device sensor 116, but not VM sensor 116, as such packet would not flow through VM 110 _(A). Moreover, a packet originating at, or destined to, leaf router 104 _(A), will be captured and reported by network device sensor 116, but not VM sensor 116, hypervisor sensor 116, or any other sensor on server 106 _(A), as such packet would not flow through VM 110 _(A), hypervisor 108 _(A), or server 106 _(A).

Each of the sensors 116 can include a respective unique sensor identifier on each of the reports 244 it sends to collector 118, to allow collector 118 to determine which sensor sent the report. The reports 244 used to analyze network and/or system data and conditions for troubleshooting, security, visualization, configuration, planning, and management. Sensor identifiers in the reports 244 can also be used to determine which sensors reported what flows. This information can then be used to determine sensor placement and topology, as further described below. Sensor placement and topology information can be useful for analyzing the data in the reports 244, as well as troubleshooting, security, visualization, configuration, planning, and management.

FIG. 2D illustrates an example schematic diagram of an example sensor deployment in a computing network environment communicating collector. System 260 includes host 106 ₁, 106 ₂, . . . , 106 _(x)). (herein described as host or node), sensors 116 ₁, 116 ₂, . . . 116 _(x) (herein described as sensor) and collector 118. As described above, host can include a container, virtual machine (VM), hardware network device (e.g., switch or router), hypervisor or physical server. Additionally, each host can include one or more sensors (e.g. sensor 116 ₁, 116 ₂, . . . 116 _(x)). Furthermore, as described above, the sensor can be configured to capture activity (e.g., network traffic received, transmitted, or generated by the host), and report the captured activity (including any data and/or metadata) of the host where the sensor resides. Additionally, each report can include a timestamp based on the clock of the host and/or layer of the host where the sensor resides. Furthermore a node or host can have one sensor, or a node or host can have multiple sensors. For example host 106 ₁ includes one sensor 116. In another example host 106 ₂ has two sensors 116. Furthermore since each report includes a timestamp based on clock(s) where each of the sensors 116 resides, the timestamp of sensors 116 can be based on the same clock or different clock, depending on where sensors 116 reside. For example, assume the clocks of host 106 ₁ and 106 ₂ differ (i.e., are not synchronized). As such the timestamps of the report(s) of sensors 116 residing on host 106 ₂ are based on the same clock of host 106 ₂.

However the timestamp(s) of the report(s) of sensors 116 residing on host 106 ₁ can be different from the respective timestamp(s) of the report(s) of sensors 116 residing on host 106 ₂ because the clocks of host 106 ₁ and host 106 ₂ have different clocks. Therefore even if the reports from sensors are transmitted and/or generated at the same time, and/or even if the networking activities occurred at the same time at host 106 ₁ and host 106 ₂, the timestamp(s) of the report(s) of sensors 116 residing on host 106 ₁ and host 106 ₂ can still be different. For example, the report from sensor 116 residing on host 106 ₁ and the report from sensor 116 residing on host 106 ₂ capture the same network event occurring concurrently at the same time on both host 106 ₁ and host 106 ₂. However, the clocks of host 106 ₁ and host 106 ₂ are different. As such the timestamp of the report of sensor 116 residing on host 106 ₁ is 1 P.M. and the timestamp of the report of sensor 116 residing on host 106 ₂ is 2 P.M., even though both events reported are the same event and occurred simultaneously on both host 106 ₁ and host 106 ₂, at 1:15 P.M. Both timestamps are different even though they are intended to refer to the same event occurring at the same time.

The collector (e.g. collector 118) can be a group of processes running on a single machine or a cluster of machines capable of doing preprocessing and analysis of data collected from a sensor. The collector is configured to receive data from the one or more sensors. It should be noted that a system can include multiple collectors. However, for sake of simplicity, in this disclosure, all collectors are treated as one logical entity. Multiple sensors can report data to a collector. Moreover, a specific sensor can report data to a specific collector. Sensors and the collector are not limited to observing and processing just network data, but can also capture other information, such as, currently active processes, active file handles, socket handles, status of I/O devices, memory, etc.

In some situations, the clock of the collector is not synchronized with the clock of one or more hosts. As such, the collector may attribute an incorrect time to activities at the one or more hosts (which may affect its ability to identify sequence of events, correlate events, perform analytics of data flows and events, determine even lineage, etc.), because the collector or any other analytic engine could be receiving data reports with inconsistent timestamps. For example, one data report timestamp for an event or network activity of a host, occurs at 9 PM but the clock of the collector is at 8:30 PM when receiving the data report. This can present a challenge to the collector or any other entity when trying to analyze or interpret that data report.

An example method to synchronize the timestamp of a sensor report to the clock of a collector is illustrated in FIG. 3A and FIG. 3B. The example method to synchronize can help alleviate the problem of the inconsistent timestamps of data reports, and associated reported data to respective times with greater accuracy. The example method is disclosed in two parts—the first part pertaining to the determination of delta(Δ) or the difference between the clock of the collector and the clock of the host/node, and the second part pertaining to the determination of a latency associated with a channel between a particular sensor and the collector. The collector can synchronize the timestamp of one or more reports from one or more sensors. The first part of the method is illustrated in FIG. 3A. FIG. 3A illustrates an example method for determining the clock differences or A between a sensor or multiple sensors residing on one or more hosts and a collector. Method 302 begins with a collector receiving a report from a sensor, of observed network activity of a host where the sensor resides. For example, as illustrated in FIG. 2D, sensors 116 at host 106 ₁ (e.g. a server or virtual machine) sends a report of observed network activity of host 106 ₁ to collector 118. The report includes a timestamp indicating when the sensor sent the report to collector 118, where the timestamp is based on the clock of the host where the sensor is located.

At step 306, the collector determines and associates a timestamp indicating when the collector received the data report. The second timestamp is based on the clock of the collector. For example, in FIG. 2D, once collector 118 receives the report from sensors 116, collector 118 determines and associates a timestamp indicating when the collector received the report from the sensor collector 118

At step 308, the collector determines the Δ. The Δ is the difference between the two timestamps (the timestamp indicating when the collector received the report from the sensor and the timestamp included in the data report indicating when the data report was generated and/or transmitted). By determining Δ, the collector can identify the clock of the sensor relative to the collector's clock. Furthermore since the clock of the sensor is based on the clock of the host system where the sensor resides, Δ also identifies the clock of the host relative to the collector's clock.

However, it can take time for a message or packet to travel from one node to another. As such some margin of error or latency can be present between a collector and a sensor. Latency can include a round-trip latency, a single hop latency, single leg latency, single path latency, network latency, system latency (e.g. processor or memory latencies), route-specific latency, etc. Determining a latency or latency range or bound associated with a communication channel between a sensor and a collector, determines an error margin of the identified Δ. At step 310, the collector adjusts Δ based on the determined communication latency. The determination of a latency associated with a communication channel between a sensor and a collector will be discussed later below, in further detail.

Once the collector adjusts Δ based on the determined latency, at step 312, the collector can generate a new timestamp based on the adjusted Δ. The collector can associate the new timestamp based on the adjusted Δ with the report. The collector can replace the timestamp of the data report with the new timestamp. This will synchronize the timestamp designated for the report to be relative to the clock of the collector. Additionally, the synchronized timestamp of the report can account for some margin of error based on the determined latency.

In some situations, synchronizing the timestamps/clocks of the host relative to the clock of the collector, can help determine a sequence of network activity or events reported. For example, sensors 116 send multiple data reports to collector 118. Each report, as discussed above, includes timestamps relative to the clock of the host (e.g. 8:31 AM, 8:32 AM, 8:33 AM . . . ) and data of observed network activity of the host. However the clock of the collector and the clock of the host are not synchronized (e.g. 7:00 AM). In accordance with the method above, collector 118 synchronizes the timestamps of the data reports from sensors 116 to the clock of collector 118 with an account for some margin of error based on the determined communication latency. As such, the collector or some other analytics engine determines a sequence of events. The collector or some other analytics engine can generate a timeline on a user interface (UI). The timeline can include various sensor reports that have been synchronized to the clock of the collector, which can include an account for some margin of error based on the determined latency for the sensor. The timeline can allow a user to visualize the sequence of events described for a particular host where the sensor is residing.

In some situations, synchronizing the timestamps/clocks of the host relative to the clock of the collector, can determine a sequence of network activity or events of a computing environment (e.g. multiple hosts in a network). For example, sensors 116 on host 106 ₁ and host 106 ₂ send multiple reports to collector 118. The report from sensors 116, includes a timestamp relative to the clock of host 106 ₁ (e.g. 8:31 AM) and data of observed network activity of the host 106 ₁. Similar to the report from sensors 116 on host 106 ₁, 106 ₂ includes data of observed network activity of the host including events, and a timestamp relative to the clock of host 106 ₂ (e.g. 9:32 AM). However the clock of the collector and the clock of the host 106 ₁ and 106 ₂ are not synchronized (e.g. 7:00 AM). In accordance with the method above, the collector synchronizes the timestamps of the reports from sensors 116 on both host 106 ₁ and 106 ₂ to the clock of collector 118 with an account for some margin of error based on the determined latency for each sensor. As such, collector 118 or some other analytics engine determines a sequence of events captured from multiple sensors (e.g. 264 ₁ and 264 ₂). Collector 118 or some other analytics engine can generate a timeline on a UI of various events in the network environment. The timeline can include data reports that have been synchronized to the clock of the collector, which may account for some margin of error based on the determined latency associated with a communication channel of each sensors 116 and collector 118. The timeline can allow a user to visualize the sequence of events described in one or more data reports.

The adjustment of timestamps above can be helpful in the security context. For example, a malicious attack occurs over multiple hosts and/or processes. The disclosed techniques can reveal the sequence of the attacks over multiple hosts, the origin of the attack, the sequence of processes, the triggering events, and the relationships between triggers and events. For instance, referencing back to the example above, assume above process on host 106 ₁ has triggered an attack or malicious event on host 106 ₂. Since sensors 116 observe network activity of host 106 ₁ and host 106 ₁ respectively, sensors 116 data reports to collector 118. The report from sensors 116 on host 106 ₁, includes a timestamp of the process relative to the clock of host 106 ₁ (e.g. 8:34 AM) and data describing the process. The report from sensors 116 on host 106 ₂ includes data describing the malicious attack or event, and a timestamp of the malicious attack or event relative to the clock of host 106 ₂ (e.g. 8:32 AM). However the clock of the collector and the clock of the host 106 ₁ and 106 ₂ may not be synchronized (e.g. 7:00 AM). In accordance with the method above, collector 118 can synchronize the timestamps of each report from sensors 116 to the clock of the collector to estimate the time of each report relative to the clock of collector 118. The estimated times can also account for some margin of error based on the determined communication latency. As such, the collector or some other analytics engine can determine a sequence of the events at multiple sensors, and any relevant relationship details (e.g., lineage, etc.). In the example above, collector 118 or some other analytics engine can determine that the malicious attack originated with host 106 ₂ and proceeded to host 106 ₁ (assuming no other malicious attacks were reported by other sensors 116).

Furthermore, the collector or some other analytics engine can generate a timeline that includes synchronized data reports of one or more hosts, optionally with an account for some margin of error based on the determined communication latency. The timeline can allow a user to visualize the sequence of events of the malicious attack described in one or more data reports.

The collector can use a previously-calculated latency or error margin to synchronize the timestamps of the sensor reports until a predetermined threshold (e.g. time or detecting of abnormally large or small communication latency). For example, a collector can use a generated timestamp based on a current adjusted Δ until after a predetermined time threshold has passed. For instance, the predetermined time threshold is a day, and the collector will use a generated timestamp based on the current adjusted Δ until a day has passed. Once a day has passed, the collector can use the above described techniques to generate a new adjusted timestamp based on a newly determined latency, error margin, etc. The collector can then apply the newly generated latency and/or error margin on subsequently (after the new timestamp has been generated) received sensor reports until another day has passed.

FIG. 3B illustrates an example method for determining a communication latency associated with the communication channel between the collector and the sensor(s). The communication latency can be calculated before or after determining Δ.

Method 350 begins at step 355 where the collector sends a request message to a sensor, such as a heartbeat or request-reply message. The request message requests the sensor to send a reply message to the collector. As such, once the sensor receives the request message, the sensor sends a reply message back to the collector. The sensor can use the same channel as with the transmission of the request packet by the collector. The sensor can also use a different channel than the channel used for transmitting the request packet by the collector. The reply message includes a timestamp indicating when the sensor sent the reply message based on the host clock of where the sensor resides. Additionally, at step 360, when the collector sends a request message to the sensor, the collector can associate a timestamp for when the collector sent the request packet. For example, as illustrated in FIG. 4A, collector 118 sends a request packet to sensors 116 and associates a timestamp of when collector 118 sent the request packet.

At step 365, collector 118 receives the automatic reply packet from sensors 116, and at step 370, collector 118 determines a time and/or associates a timestamp indicating when the collector received the automatic reply packet. For example, in FIG. 5B, since the request packet is configured to trigger automatic reply by the sensors 116, immediately sends a reply packet to collector 118. Collector 118 then determines and/or associates with the reply packet a timestamp indicating when collector 118 received the reply packet.

At step 375, the collector determines a communication latency or range. The communication latency can include the time for a packet to make a round trip between a sensor and a collector. In FIG. 4B, the communication latency of interest is the round trip time it takes for a packet to travel between sensors 116 and collector 118, using the same channel. As discussed above, the communication latency can be used to calculate a margin of error for the adjusted Δ. Collector 118 can determine a communication latency based on one or more reply messages. For example, collector 118 can determine the latency based on the average of the between the timestamp indicating when collector 118 sent the request message to sensors 116 on a communication channel, and the timestamp indicating when the collector received the reply message from sensors 116 on the same communication channel.

The collector can determine a communication latency by also incorporating the timestamp included in the reply packet from the sensor. For instance, the collector can add the new timestamp based on the adjusted Δ with the report. As such the report can include both the new timestamp and the timestamp based on the clock of the sensor. For example, as illustrated in FIG. 2D, collector 118 can add the new timestamp based on the adjusted Δ with the report from sensor 116 of host 106 ₁. As such the report can have both the new timestamp and the time stamp based on the clock of host 106 ₁ where sensor 116 is located.

The collector can determine Δ and the associated communication latency continuously on a periodic basis to ensure the collector maintains accuracy over time.

Using the above described techniques, the collector can also determine multiple communication latency for a single determination of Δ. For example, the collector can send multiple request messages to a sensor, to determine multiple communication latency ranges of one channel. Additionally, the collector can determine or associate a timestamp indicating when the collector sent the request messages. Once the sensor(s) receives the request messages, the sensor(s) can send a reply message back to the collector. Each reply message includes a timestamp indicating when the sensor sent the reply message to the collector and each timestamp can be based on the clock of the host where the sensor resides. After the collector receives the reply messages from the sensor, the collector determines or associates another timestamp indicating when the collector received the reply messages from the sensor. The collector can calculate respective latencies based on the timestamps associated with each request-reply message. Once the collector determines communication latency ranges for all request packets (e.g. determining the difference between the timestamp indicating when the collector sent the request message and the timestamp of when the collector received the reply message), the collector determines a communication latency and/or range to apply to the determined Δ.

The collector can store a history of communication latency associated with a communication channel between a collector and a sensor communicating with that collector (herein described as the historical fashion). Based on the history of communication latencies associated with a communication channel between each sensor and the collector, the collector can determine a historical communication latency to apply to the Δ. Additionally, the collector can calculate the media or average of multiple historical communication latency. Furthermore, the collector can determine abnormal historical communication latency (e.g. communication latency that are either unusually large or small compared to the average historical communication latency or the median historical communication latency). The collector can identify the abnormal latency and determine whether to include or exclude any.

The collector can determine communication latency in either in a historical fashion or in the other methods described above. For example, in some embodiments, the collector selects a communication latency based one or more predetermined condition. For example, the collector determines the historical fashion includes a few abnormally large or abnormally small communication latency, as compared to the average historical communication latency. As such, instead, the collector selects the communication latency based on the method described in FIG. 3B. In some embodiments, the predetermined threshold is based on a predetermined time. For instance, after a predetermined time, the collector selects the communication latency based on any of the above described techniques.

The collector or some other analytics engine can use all of the above-described techniques to synchronize or adjust all the internal clocks of the hosts in the data center. This of course assumes that the collector has complete access to the host or the system of the data center. For example, the collector determines an adjusted Δ based on the determined communication latency of a particular sensor. In turn the collector adjusts or synchronizes the internal clock of the host where the particular sensor resides based on the adjusted Δ. Furthermore, in some embodiments this can be done for all the hosts with sensors operatively communicating with the collector.

FIG. 5 illustrates an example network device 510 according to some embodiments. Network device 510 includes a master central processing unit (CPU) 562, interfaces 568, and a bus 515 (e.g., a PCI bus). When acting under the control of appropriate software or firmware, the CPU 562 is responsible for executing packet management, error detection, and/or routing functions. The CPU 562 preferably accomplishes all these functions under the control of software including an operating system and any appropriate applications software. CPU 562 may include one or more processors 563 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 563 is specially designed hardware for controlling the operations of router 510. In a specific embodiment, a memory 561 (such as non-volatile RAM and/or ROM) also forms part of CPU 562. However, there are many different ways in which memory could be coupled to the system.

The interfaces 568 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the router 510. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast token ring interfaces, wireless interfaces, Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 562 to efficiently perform routing computations, network diagnostics, security functions, etc.

Although the system shown in FIG. 5 is one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. is often used. Further, other types of interfaces and media could also be used with the router.

Regardless of the network device's configuration, it may employ one or more memories or memory modules (including memory 561) configured to store program instructions for the general-purpose network operations and mechanisms for roaming, route optimization and routing functions described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store tables such as mobility binding, registration, and association tables, etc.

FIG. 6A and FIG. 6B illustrate example system embodiments. The more appropriate embodiment will be apparent to those of ordinary skill in the art when practicing the present technology. Persons of ordinary skill in the art will also readily appreciate that other system embodiments are possible.

FIG. 6A illustrates a conventional system bus computing system architecture 600 wherein the components of the system are in electrical communication with each other using a bus 605. Exemplary system 600 includes a processing unit (CPU or processor) 610 and a system bus 605 that couples various system components including the system memory 615, such as read only memory (ROM) 670 and random access memory (RAM) 675, to the processor 610. The system 600 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 610. The system 600 can copy data from the memory 615 and/or the storage device 630 to the cache 612 for quick access by the processor 610. In this way, the cache can provide a performance boost that avoids processor 610 delays while waiting for data. These and other modules can control or be configured to control the processor 610 to perform various actions. Other system memory 615 may be available for use as well. The memory 615 can include multiple different types of memory with different performance characteristics. The processor 610 can include any general purpose processor and a hardware module or software module, such as module 1 637, module 2 634, and module 3 636 stored in storage device 630, configured to control the processor 610 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 610 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing device 600, an input device 645 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 635 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 600. The communications interface 640 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 630 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 675, read only memory (ROM) 680, and hybrids thereof.

The storage device 630 can include software modules 638, 634, 636 for controlling the processor 610. Other hardware or software modules are contemplated. The storage device 630 can be connected to the system bus 605. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 610, bus 605, display 635, and so forth, to carry out the function.

FIG. 6B illustrates an example computer system 650 having a chipset architecture that can be used in executing the described method and generating and displaying a graphical user interface (GUI). Computer system 650 is an example of computer hardware, software, and firmware that can be used to implement the disclosed technology. System 650 can include a processor 655, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. Processor 655 can communicate with a chipset 660 that can control input to and output from processor 655. In this example, chipset 660 outputs information to output 665, such as a display, and can read and write information to storage device 670, which can include magnetic media, and solid state media, for example. Chipset 660 can also read data from and write data to RAM 675. A bridge 680 for interfacing with a variety of user interface components 685 can be provided for interfacing with chipset 660. Such user interface components 685 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. In general, inputs to system 650 can come from any of a variety of sources, machine generated and/or human generated.

Chipset 660 can also interface with one or more communication interfaces 690 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 655 analyzing data stored in storage 670 or 675. Further, the machine can receive inputs from a user via user interface components 685 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 655. It can be appreciated that example systems 600 and 650 can have more than one processor 610 or be part of a group or cluster of computing devices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. Moreover, claim language reciting “at least one of” a set indicates that one member of the set or multiple members of the set satisfy the claim. 

The invention claimed is:
 1. A computer-implemented method, comprising: receiving, by a network analytics system, first sensor data, including first network activity and a first timestamp associated with a first clock of a first node of a data center, from a first sensor of the first node, and second sensor data, including second network activity and a second timestamp associated with a second clock of a second node of the data center, from a second sensor of the second node; determining, by the network analytics system, a first delta between the first clock and a third network clock of the network analytics system based on the first timestamp, and a second delta between and the second clock and the third clock based on the second timestamp; determining, by the network analytics system, a first communication latency between the network analytics system and the first sensor, and a second communication latency between the network analytics system and the second sensor; and generating, by the network analytics system, a report that synchronizes one or more data flows between the first node and the second node based on the first delta, the second delta, the first communication latency, and the second communication latency.
 2. The computer-implemented method of claim 1, further comprising: identifying a first Layer 7 process executing within the first node that initiates the one or more data flows based on the report.
 3. The computer-implemented method of claim 2, further comprising: identifying a second Layer 7 process executing within the second node in response to initiation of the one or more data flows based on the report.
 4. The computer-implemented method of claim 2, further comprising: identifying a user associated with the first Layer 7 process based on the report.
 5. The computer-implemented method of claim 2, further comprising: determining an amount of at least one of central processing unit (CPU) utilization, memory utilization, or storage utilization associated with the first Layer 7 process based on the report.
 6. The computer-implemented method of claim 1, further comprising: identifying a network attack that initiates the one or more data flows based on the report.
 7. The computer-implemented method of claim 1, further comprising: receiving third sensor data including third network activity and a third timestamp associated with a clock of a switch or router; determining a third delta between the clock of the switch or router and the third clock based on the third timestamp; determining a third communication latency between the network analytics system and the switch or router; and determining a data path between the first node and the second node based on the first delta, the second delta, the third delta, the first communication latency, the second communication latency, and the third communication latency.
 8. The computer-implemented method of claim 7, further comprising: receiving fourth sensor data including fourth network activity and a fourth timestamp associated with a clock of a firewall; determining a fourth delta between the clock of the firewall and the third clock based on the fourth timestamp; and determining a fourth communication latency between the network analytics system and the firewall, wherein the data path is further determined based on fourth delta and the fourth communication latency.
 9. The computer-implemented method of claim 1, wherein the first node and the second node reside within a same physical server.
 10. The computer-implemented method of claim 1, wherein the first report is received by a first collector of the network analytics system and the second report is received by a second collector of the network analytics system.
 11. A system, comprising: one or more processors; memory including instructions that, when executed by the one or more processors, cause the system to: receive first sensor data, including first network activity and a first timestamp associated with a first clock of a first node of a data center, from a first sensor of the first node, and second sensor data, including second network activity and a second timestamp associated with a second clock of a second node of the data center, from a second sensor of the second node; determine a first delta between the first clock and a third clock of the network analytics system based on the first timestamp, and a second delta between and the second clock and the third clock based on the second timestamp; determine a first communication latency between the network analytics system and the first sensor, and a second communication latency between the network analytics system and the second sensor; generate a report that synchronizes one or more data flows between the first node and the second node based on the first delta, the second delta, the first communication latency, and the second communication latency; and identify a first Layer 7 process executing within the first node that initiates the one or more data flows based on the report.
 12. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: identify a second Layer 7 process executing within the second node in response to initiation of the one or more data flows based on the report.
 13. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: identify a user associated with the first Layer 7 process based on the report.
 14. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: determine an amount of at least one of central processing unit (CPU) utilization, memory utilization, or storage utilization associated with the first Layer 7 process based on the report.
 15. A non-transitory computer-readable medium including instructions that, when executed by one or more processors of a system, cause the system to: receive first sensor data, including first network activity and a first timestamp associated with a first clock of a first node of a data center, from a first sensor of the first node, and second sensor data, including second network activity and a second timestamp associated with a second clock of a second node of the data center, from a second sensor of the second node; determine a first delta between the first clock and a third clock of the network analytics system based on the first timestamp, and a second delta between and the second clock and the third clock based on the second timestamp; determine a first communication latency between the network analytics system and the first sensor, and a second communication latency between the network analytics system and the second sensor; and generate a report that synchronizes one or more data flows between the first node and the second node based on the first delta, the second delta, the first communication latency, and the second communication latency.
 16. The non-transitory computer-readable medium of claim 15, further comprising further instructions that, when executed by the one or more processors, further cause the system to: identify a network attack that initiates the one or more data flows based on the report.
 17. The non-transitory computer-readable medium of claim 15, further comprising further instructions that, when executed by the one or more processors, further cause the system to: receive third sensor data including third network activity and a third timestamp associated with a clock of a switch or router; determine a third delta between the clock of the switch or router and the third clock based on the third timestamp; determine a third communication latency between the network analytics system and the switch or router; and determine a data path between the first node and the second node based on the first delta, the second delta, the third delta, the first communication latency, the second communication latency, and the third communication latency.
 18. The non-transitory computer-readable medium of claim 17, further comprising further instructions that, when executed by the one or more processors, further cause the system to: receive fourth sensor data including fourth network activity and a fourth timestamp associated with a clock of a firewall; determine a fourth delta between the clock of the firewall and the third clock based on the fourth timestamp; and determine a fourth communication latency between the network analytics system and the firewall, wherein the data path is further determined based on fourth delta and the fourth communication latency.
 19. The non-transitory computer-readable medium of claim 17, wherein the first node and the second node reside within a same physical server.
 20. The non-transitory computer-readable medium of claim 17, wherein the first report is received by a first collector of the system and the second report is received by a second collector of the system. 